Repository navigation
Plot each MATLAB quality history using its actual iteration count - #813
Merged
AnderBiguri merged 1 commit intoNov 10, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The MATLAB quality demo concatenates metric histories and pads only SART to the OS-SART length. This fails when algorithms produce histories of different lengths, for example when SIRT stops earlier or SART runs longer than OS-SART.
Plot each algorithm's metric row against its own iteration indices. Keep the metric titles and algorithm legends without padding or assuming equal history lengths.
Validation: a live MATLAB R2020a regression executes the plotting section with four permutations of unequal histories, including an empty history. Upstream
aea5346fails with a concatenation-dimension error; the fixed version passes checks of plotted values, metric rows, labels and iteration indices. This is a CPU plotting regression, not a CUDA reconstruction test.